Using DOORS v71102 (still)
I baselinde a modue as I usually do, but the server crashed during the process.
When I attempt to open the module (even read-only) now, I get "Unable to open module <fullname>, Lock request timed out".
I've run a small script to identify the module's unique identifier and had a look in the appropriate folder on the server.
In the <ID>.mod folder, there are the usual folders and files I would expect:- bnnnnnnnn.bas folders for each baseline, the current.ver and views folders, plus dir.ver, baseline.ixb/ixc, fontinfo.dtb/dtc, module.dtb/dtc
So, everything appears to be as normal, except that the current.ver folder has not only .dtb and .dtc file, but also .dtn files.
I'm reluctant to touch these withotu knowing what they are. I'm guessing they are some sort of temporary file used during the baselining process, but what else is likely to be affected?
Any ideas?
Dartguru - Wed May 12 11:02:12 EDT 2010 |
Re: Unable to open module after baseline failure
SystemAdmin - Mon May 17 15:28:26 EDT 2010 kabr - Fri May 14 07:20:11 EDT 2010
Hi Dartguru,
find out who has a lock on the module.
If it is you, then I'd say you can safely unlock the module.
If it is someone else, then contact him and have him unlock the module.
I would recommend not to mess with the actual database files if you can avoid it.
rgds
Karl
You will likely need to log on as Administrator to see if your Dataguru Database Manager user has a lock on the module that was being baselined when the crash hit you.
Typically, you cannot see shared and exclusive edit locks from your own normal Database Manager type user login screen and Manage Locks utility window, but can see all the other users who have modules open for editing with various locks.
ie. another Database Manager user would likely see the lock from the user you were logged on with when you were conducting the baseline.
gsdguy
|
Re: Unable to open module after baseline failure
jsarkic - Tue Jun 01 08:14:08 EDT 2010
I've run into the same problem with DOORS 8.3 and 9.2. A problem report has been submitted to IBM, but no solution has been found. IBM did request a copy of our data, but for security reasons, I could not ship our data to them. Our only solution was to restore the corrupted module from a backup, and re-create all traceability links.
|